To start off the battle to the death, let's compare Requirements to see if the browsers are compatible with the average system.
As for HTML3.2 functions, AWeb supports more of them then Voyager, many people who tried AWeb 1.2 said that it was terrible as it didn't support any HTML3.2 standards. And they were right, but don't let that bias your opion of AWeb 2.0, it does backdrops, background colors, transparent gifs, link colors, line sizing, 'virtual frames'. I could list all of the two browsers functions, but that would take pages of text. Instead I will show the differences betweeen the two.
Voyager does not support line sizing, (see Voyager screenshot and Aweb screenshot) where AWeb does, however Voyager does support Telnet by calling an external program to handle it. At the moment AWeb does not. Both can do the 'mailto:' function with plugins, and both will do FTP, Voyager internally and AWeb with the FTP plugin. One function that Voyager lacks and is 'vitural frames' AWeb supports this. It is not actually frames like you would see on Netscape, but instead it recognizes the frame command and will give you links to the different frames so you aren't missing any information. Voyager completely ignores the frame command.
As for graphic display, both will look similar displaying inline gifs and jpegs as both use datatypes on your computer. With v43 of the datatypes both will use a 64,000 color palette (When using our Picasso card, with AGA it will use a 256 color pallete, and a 16 color pallete for other chipsets). As for the Icons for navigating with the browser, it depends on personal preference. Voyager has large attractive icons, and AWeb has more compact 4 color icons. One other neat function in AWeb is if you click on the lightning bolt icon it will give you a display of what network activity is currently happening.
Configurability is another subject where AWeb rises above Voyager, in both you can configure your Fonts, proxies, cache sizes, but AWeb will let you choose your own screen mode straight from the program. In Voyager this must be done through MUI. AWeb also has 3 different HTML settings, 'Strict' 'Tolerant' and 'Compatible', to adjust what AWeb will display and accept. If AWeb meets a command it does not recognize in 'Strict' mode it will disregard it.
Without v43 datatypes
AWeb 84% | Yoyager 87%